ci: alert Slack on release failure - #5
Conversation
|
Warning Review limit reached
Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release workflow adds a ChangesFailure notification
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant Build as build job
participant Release as release job
participant Notify as notify-failure job
participant Slack as Slack webhook
Build-->>Notify: job result
Release-->>Notify: job result
Notify->>Slack: post failure payload
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
cfbf66d to
bc09576
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/build-release.yaml:
- Line 63: Replace the mutable v2.1.0 tag in the Slack action step with the full
immutable commit SHA corresponding to slackapi/slack-github-action v2.1.0,
preserving the release notification configuration and webhook usage.
- Line 75: Update the Slack payload’s commit reference near the notification
template to avoid inserting github.event.head_commit.message directly; use
github.sha or a separately generated, escaped and length-limited JSON-safe value
instead, while preserving the existing commit context in the message.
- Around line 62-66: Update the “Notify Slack on release failure” step using
slackapi/slack-github-action@v2.1.0 to enable its error-failing behavior by
setting the action’s errors input to true, so non-200 Slack responses fail the
notification job.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 0219e7d9-9cdb-4282-8a3b-12de19362abb
📒 Files selected for processing (1)
.github/workflows/build-release.yaml
Add a notify-failure job to build-release.yaml that posts to the PLATFORM_INCIDENT_SLACK_CHANNEL_WEBHOOK Slack channel only when the release fails (guarded by if: failure()). Successful releases are unaffected.
bc09576 to
3fdccbb
Compare
2 participants
Adds a
notify-failurejob tobuild-release.yamlthat posts a Slack alert when the release pipeline fails.